EnigmA Amiga Run 1997 May

home *** CD-ROM | disk | FTP | other *** search

/ EnigmA Amiga Run 1997 May / EnigmA AMIGA RUN 18 (1997)(G.R. Edizioni)(IT)[!][issue 1997-05][EAR-CD II].iso / recent2 / aemail.lha / aemail115 / INSTALL.TXT < prev next >

Wrap

Text File | 1997-04-06 | 23KB | 427 lines

INSTALLATION OF AEMAIL (April 5, 1997) PLEASE NOTE: If you are installing from an AEMail installation disk, that disk must NOT be write protected when you install AEMail. It will be written to during the install. If you need further information on the AEMail install and some of the items mentioned in this document, please consult either the "AEMail.guide" or the "AEMail.doc" documents on the AEMail installation diskette (or the AEMail archive). The AEMail Install Script uses the Installer program first provided by Commodore and later revised by Amiga Technologies. Installer and Installer project icon (c) Copyright 1995-96 Escom AG. All Rights Reserved. Reproduced and distributed under license from Escom AG. INSTALLER SOFTWARE IS PROVIDED "AS-IS" AND SUBJECT TO CHANGE; NO WARRANTIES ARE MADE. ALL USE IS AT YOUR OWN RISK. NO LIABILITY OR RESPONSIBILITY IS ASSUMED. An installation script has been provided for the installation of AEMail. To install AEMail simply double click on the "Install_AEMail icon". The install script provides three user levels that the user can choose: Novice (no control - all defaults will be taken) Intermediate (control of configuration parameters) Expert (control of configuration and where files are placed) The Install script makes an attempt to determine which TCP/IP stack that you have installed. This controls which defaults will be taken. The way the install scripts knows which TCP/IP stacks are present is as follows (you must have installed the particular stack before installing AEMail): AmiTCP: This is controlled by the presence of the AmiTCP: assign statement and the presence of the AmiTCP:bin drawer. Miami: This is controlled by the presence of the Miami: assign statement. When you installed Miami you should have let the install create the Miami: assign. This was only available under later versions of Maimi. While the Miami: assign is not an absolute requirement if you are using Miami, it is required if you intend to use the supplied "startnet.miami" and "stopnet.miami" scripts supplied with this archive. The scripts will not even be moved to your AEMail drawer if the Miami: assign is not present. TermiteTCP: This is controlled by the presence of the TermiteTCP.prefs envronomental variable. Also, if you want to pick up some of the other TermiteTCP variables, such as email address, you must have run TermiteTCP prior to installing AEMail (TermiteTCP does not have to be online, however). The action that takes place at the Novice level is slightly different depending on whether AmiTCP has been installed or not. The installation script determines if AmiTCP is installed by checking for an assignment to AmiTCP:. This AmiTCP: assignment was automatically created when you installed AmiTCP. The AmiTCP: assignment determines where the installation script will place the AEMail executable. For AmiTCP the executable is placed in the AmiTCP:bin drawer. If it is not present, the placement of the executable defaults to an AEMail drawer (created by the script if it does not already exist) on the largest partition on your hard drive. If you wish to control where AEMail will be placed, you will need to execute the Install script at the "Expert" user level. The reason that AEMail is placed in the AmiTCP:bin drawer is that the assumption is made that you are using AmiTCP. The "startnet" and "stopnet" scripts should be in the same directory that contains AEMail if they are to work without modification. If you select the Novice user level you will not be able to give any input for the install. The following actions will automatically be taken: The AEMail executable file will be placed in AmiTCP:bin or, if the AmiTCP: assignment is not present, on the largest partition on your hard drive. Note: No special directory will be created if AmiTCP:bin is present, otherwise a directory called "AEMail" will be created for containing the AEMail executable. When the installation script terminates it will tell you where it placed the AEMail executable. The AREXX scripts StartNet.Miami and StopNet.Miami will also be moved to this drawer if you have Miami installed on your system. Your AEMail mail directory will normally be a directory called AEMail_Mail in AmiTCP: or, if AmiTCP: was not present, in the AEMAIL directory. The AEMail mail directory will be assigned to AEMAIL:. If an AEMAIL: assignment already exists, that directory will be used as the mail directory except that it will be renamed to AEMail_Mail if it had been named something else. This operation is automatic and makes updating the AEMail program easy without disturbing your existing mail files. No configuration will be performed. However, certain default configuration values will be provided (see below). This will include the appropriate Start Net and Stop Net scripts for the TCP/IP stacks that you are running. Miami takes precedence over AmiTCP. All of the documentation files will be copied to the same drawer in which the AEMail executable was copied to. If you are running under AmigaDos 3.0 or greater, the supplied mailcap file will be copied to the AEMail_Mail directory. No mailcap file will be copied if you are using AmigaDos 2.1. An AEMAIL: assign statement will automatically be placed in your S:User-Startup file. An "ASSIGN C: SYS:REXXC ADD" will also be added to your s:User-Startup file to provide a path to your AREXX commands. If you select the Intermediate user level you will also be able to provide configuration data that will be stored in the Tool Types parameters of the AEMAIL icon. Further, if the AEMAIL: assignment existed at the start of the installation that assignment will be used. However, if the mail directory had been called something else, you will be asked if you want to rename it to AEMail_Mail. If you select NO, the directory will not be renamed; however, a new AEMail_Mail directory will be created in the same parent directory and used for the AEMAIL: assignment. In addition to what is available for the Intermediate user, the Expert user will be able to select what directories will be used and will be able to copy the documentation files to a directory of his/her choice. The Expert user will also be able to select an alternate location for a pre-existing mailcap file and, if running under AmigaDos 2.1, will be able to build their own mailcap file. Certain configuration parameters must be provided before AEMAIL will run. These configuration parameters are provided either by Tool Types in the AEMail icon or through a special configuration screen when you first run AEMail and saved in an aemail.cnfg file in the S: directory. For a full discussion on configuring AEMail, refer to the AEMail documentation or guide files. The installation script will try to automatically configure certain items to default values. These include the switch for deleting mail from your POP Server once it has been transferred to your Amiga and the switch for stripping duplicate messages. The edit call will default to c:ed and will open the editor on the Workbench. Also, if you installed TermiteTCP, the installation script will obtain your POP3 UserID and SMTP Domain Name as well as your email address from the ttcp-email-address environmental variable provided TermiteTCP has been run (not necessarily on-line) before the AEMail installation was performed. The installation script at the Intermediate and Expert user levels will allow you to provide additional configuration parameters as Tool Types in your AEMail icon or to change the default ones. However, if you are updating from a prior version you may already have an aemail.cnfg file in your S: directory which will override the Tool Types. If the S:aemail.cnfg file is present, you will be asked if you want to use it or if you want to re-configure using tool types. If you select this option your current s:aemail.cnfg file will be deleted and you can reconfigure through the installation script. If these parameters are not provided by Tool Types (through the installation script) or by an existing configuration file, the Configuration screen will be displayed upon the initial startup of AEMail. You can not proceed beyond this configuration screen until certain required configuration parameters are provided. The absolute minimum configuration parameters that must be provided are: POP3 UserID Password Your email Address SMTP Domain Name Edit Call A POP Server name and a SMTP Server name must also be provided. However, if they are missing AND, if the SMTP Domain Name has been specified, default values will be assigned to these items. These default values will prepend 'POP." to the domain name for the POP server and 'SMTP.' to the domain name for the SMTP Server as defaults. Please note: these may NOT be correct for your POP and SMTP servers. If they are not, you will have to edit the Configuration and make appropriate changes (see Configuration Parameters for Identify under Section IV. Configuration in the doc file or the section on the Configuration screen in the .guide file). If you have installed and ran TermiteTCP before you installed AEMail, the only configuration parameter you may have to provide is your password. The POP3 UserID and the SMTP Domain Name are extracted from the email address that you gave TermiteTCP. If these are not the correct values you will have to change them in the Identity page of the Configuration screen. For AmiTCP or Miami users, you will need to provide your POP3 UserID and SMTP Domain name as well as your email address. One of the things that is needed to run AEMail is an editor. By default AEMail will use the AmigaDOS editor, ed, which comes with all Amigas. However, you can change this through the install to any editor that you want provided that you have specified that you want to configure AEMail when you do the install. Special considerations have to be made if you want to use CygnusEd (CED) as your editor. The installation script will automatically handle this by asking if you are using CygnusEd. If you are using AmiTCP, it is recommended that you place AEMail in the same directory that contains your AmiTCP StartNet and StopNet scripts (usually AmiTCP:bin) although this is not an absolute requirement. If the directory containing your StartNet or StopNet scripts is NOT the AmiTCP:bin directory or the scripts have names different from "startnet" or "stopnet", you will have to add the STARTNET and STOPNET tool types to your AEMail icon. You can do that with the installation script at either the Intermediate or Expert user levels. If you are using TermiteTCP, there are no Start Net or Stop Net scripts. For Miami, special startnet.miami and stopnet.miami scripts have been provided with the install of AEMail. If the Miami assign is present, the install script assumes the Miami startnet and stopnet scripts should be used over the AmiTCP ones. SPECIAL NOTE FOR MIAMI USERS: In the TCP/IP Settings page on Miami, the "Down when Offline" item should be checked and the settings SAVED. If this item is not checked, it will take AEMail 80 seconds to determine that Miami is offline if Miami is loaded but not online. The installation script will automatically create a directory for your email storage (mail and configuration files) and place TWO ASSIGN statements in your S:User-Startup file as follows: ASSIGN AEMAIL: [your-mail-directory-path] ASSIGN C: SYS:REXXC ADD The second assign statement is used to provide a path to your AREXX commands because the only paths visable when you run a program from the Workbench are the program directory and C:. If you are using AmiTCP (as determined by the presence of the AmiTCP: assignment), the default directory that is created is AmiTCP:AEMail_Mail; otherwise, it will be a directory called AEMail_Mail in the AEMail directory that has been created. If an AEMAIL: assignment already exists, the AEMail_Mail directory will not be created nor will the existing mail or Configuration files in the directory be disturbed. If you want to place the AEMail_Mail directory some place else you will have to specify the Expert user level when you perform the installation. The mail directory can start out empty. The AEMail program will generate any necessary configuration and support files required. The AEMail_Mail directory can be anywhere on any one of your hard drive partitions (or on a floppy or other read/writable media); it does not have to be in the AmiTCP: directory; but it must be mounted when you execute AEMail. Special Note on Use of multiple configuration files: The normal AEMail configuration file is s:aemail.cnfg. With version 1.13 you will be able to assign your configuration file to some other name and location (you will need the Expert user level to do this). and this will become your base configuration. Also, the installation will ONLY configure this base configuration. You will have to use the Configuration screen to configure any other configuration files for other users. See Section IV., Configuration, in the doc files for other multiple user considerations. As stated above, you will need a "mailcap" file if you want to display MIME mail attachments. A sample mailcap file is provided on the AEMail program disk which uses MultiView to display audio, images, and video content types provided that you have the appropriate datatypes loaded into your system. This, of course, requires AmigaDos 3.0 or higher. If you are using AmigaDos 2.1, the mailcap file needs to be modified to reflect the display programs that you want. The installation script at the Expert level will help you do this. If you are running under AmigaDos 3.0 or higher, the installation script will automatically move the supplied mailcap file to AEMAIL: unless you specified a different location for a pre-existing mailcap file (Expert level only). The mailcap file specifications are given in AEMail documentation and guide files, When the installation script terminates it will store the directory in which it placed AEMail in the Environmental variable AEMail_dir. This facilitates updating to future releases of AEMail. The version 1.13 installation script, at all installation levels, will look for this Environmental variable to try to determine where to place AEMail. HANDLING OF TIME ZONES IN AEMAIL -------------------------------- AEMail will handle time zones in both full hour and half hour increments. AEMail uses either the "tz" environmental variable, a special "aem_tz" environomental variable, or the "locale.prefs" file that is part of AmigaDos to determine your local time zone. The "locale.prefs" file will only allow for full hour time zone offsets. You can use the "tz" environmental variable for half hour time zones, but, if this variable is used by other programs in your system it is suggested that you use the "aem_tz" variable instead. Currently AEMail first looks for the environmental variables "aem_tz" or "tz". The format for "tz" is dictated by SAS_C and should be aaabbbccc where aaa is the abbreviation for local standard time, bbb is the offset in hours from GMT (-11 to 12) which is SUBTRACTED from GMT to get the local standard time. ccc is the abbreviation for local daylight savings time or "summer time" (in the United Kingdom or Europe). If the time zone has daylight savings time this should be present even if daylight savings time is not currently in effect (contrary to the specification for "Tz" for the SAS-C compiler). AEMail automatically determines when DST or "Summer Time" is in effect. AEMail also recognizes an alternate form of "tz" where aaa and ccc can be abreviations longer than 3 characters. This is desireable in some European countries. AEMail will also recognize time zones in increments of one half hour. To specify an half hour time zone, specify it as + or - hhmm. As an example: +230 would specify a time zone in which 2 and a half hours are SUBTRACTED from GMT. You can enter the above with the "tz" environmental variable, but since this variable might be used with other programs in it's strict sense, an alternate environmental variable has been provided called "aem_tz". If "aem_tz" is present it will take precedence over "tz". If the "tz" or "aem_tz" environmental variables are not present, the system then attempts to get the time zone offset from the "locale.prefs" file. Only the time zone offset is present in this file. The abbreviations for local standard time and daylight savings time are obtained from a table that is by no means complete. Only the time zone abbreviations for the United States, Canada, and the United Kingdom are contained in this table, so one of the environmental variables is preferred. if neither the "tz" nor "aem_tz" environmental variables nor the "locale.prefs" file are present, the system defaults to CST with an offset of 6. NOTE: the standard header in an email message has the time zone offset sign reversed from that of the "locale.prefs" and the environmental variables. AEMail automatically makes this reversal, so the offset should be set to positive for US time zones and negative for European time zones. They will appear as negative (for US) and positive (for Europe) in the Date: header. You can set the "tz" or the "aem_tz" environmental variables by using the SETENV AmigaDos Command. This must be done from the shell. The syntax to use is as follows: SETENV tz aaabbbccc (for tz) and SETENV aem_tz aaaaaaaaabbbbbccccccccc (for aem_tz) aaa, your local time zone abbreviation must always be present. If you don't know your abbreviation (or don't want it in the header), use "xxx". If AEMail sees xxx it will assume that no abbreviation is present and it will be left off the Date: header bbb is the time offset in hours from GMT. Plus indicates that you are west of GMT and minus indicates that you are east of GMT. Acceptable values are -12 to 24. If you want to specify a half our time zone it can be entered as hhmm. If AEMail sees a value of 30 or above it assumes that a half hour increment is being used. In this case -1200 to 2400 are acceptable. If your time zone observes daylight savings time, ccc is the abbreviation to use for daylight savings time. If ccc is not present, no adjustment will be made during the times of the year that daylight savings time is observed. The result of the SETENV command is only in effect while your computer is on. If you want to make the "tz"or "aem_tz" environmental variables always present enter the one of the following AmigaDOS command after the SETENV command: COPY ENV:tz ENVARC:tz (or) COPY ENV:aem_tz ENVARC:aem_tz Using the "tz" or "aem_tz" environmental variables gives you more control over which abbreviations will be used for your time zone. However, the locale.prefs file may be more useful for those that prefer the "point and click" method of doing things. To set the correct time zone for locale.prefs, enter the Locale editor in your Prefs drawer. You will see a time zone map with which you can move the white strip indicating the time zone on the map. Click either to the left or right of the strip to move the strip. The correct time zone offset for standard time will be shown at the top of the map. Since the locale.prefs does not have any abbreviations, AEMail makes certain assumptions as to what the abbreviation should be. These assumptions are as follows: Time Zone Name Standard DST -----------Time Zone----------- Time (in "locale") (in email Date:) Greenwich Mean Time GMT* BST 0 +0000 Atlantic Time AST ADT 4 -0400 Eastern Time (US) EST EDT 5 -0500 Central Time (US) CST CDT 6 -0600 Mountain Time (US) MST MDT 7 -0700 Pacific Time (US) PST PDT 8 -0800 Yukon Time YST YDT 9 -0900 Hawaiian Time HST --- 10 -1000 International Date Line IDL --- 12 -1200 --- indicates this time zone does not observe DST *Note: GMT (Greenwich Mean Time) is also known as UTC or Universal Time Coordinated. If you want to use a different abbreviation or control whether DST is used or not, you should use the "tz" or "aem_tz" environmental variable. DST in the United States and Canada begins on the first Sunday in April. "Summer Time" in the United Kingdom and Europe begins on the last Sunday in March. Both DST and "Summer Time" end on the last Sunday in October.